<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Frame synchronization</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Frame_synchronization"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Frame_synchronization rootpage-Frame_synchronization skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Frame synchronization</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><style data-mw-deduplicate="TemplateStyles:r1305433154">
/* start https://en.wikipedia.org/ */
.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}
/* end https://en.wikipedia.org/ */
</style>
<p>In <a href="Telecommunications" title="Telecommunications">telecommunications</a>, <b>frame synchronization</b> or <b>framing</b> is the process by which, while receiving a stream of fixed-length <a href="Frame_(networking)" title="Frame (networking)">frames</a>, the receiver identifies the frame boundaries, permitting the <a href="Data" title="Data">data</a> bits within the frame to be extracted for decoding or retransmission.
</p><p>When packets of varying length are sent, it is necessary to have an instantly recognizable packet-end delimiter (e.g., Ethernet's <a href="Ethernet_frame#End_of_frame_–_physical_layer" title="Ethernet frame">end of stream symbol</a>). Loss of carrier signal can be interpreted as a packet-end delimiter in some cases. When a continuous stream of fixed-length frames are sent, a synchronized receiver can in principle identify frame boundaries forever. In practice, receivers can usually maintain synchronization despite transmission errors; <a href="Bit_slip" title="Bit slip">bit slips</a> are much rarer than <a href="Bit_error" class="mw-redirect" title="Bit error">bit errors</a>. Thus, it is acceptable to use a much smaller frame boundary marker, at the expense of a lengthier process to establish synchronization in the first place.
</p><p>Frame synchronization is achieved when the incoming frame alignment signals are identified (that is, distinguished from data bits), permitting the data bits within the frame to be extracted for decoding or retransmission.
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Framing">Framing</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1236090951">
/* start https://en.wikipedia.org/ */
.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}
/* end https://en.wikipedia.org/ */
</style><div role="note" class="hatnote navigation-not-searchable">"Flag sequence" redirects here. For the emojis, see <a href="Emoji_flag_sequence" class="mw-redirect" title="Emoji flag sequence">Emoji flag sequence</a>.</div>
<p>If the transmission is temporarily interrupted, or a bit slip event occurs, the receiver must re-synchronize.
</p>
<p>The transmitter and the receiver must agree ahead of time on which frame <a href="Synchronization_in_telecommunications" title="Synchronization in telecommunications">synchronization</a> scheme they will use.
</p><p>Common frame synchronization schemes are:
</p>
<dl><dt>Framing bit</dt>
<dd>A common practice in <a href="Telecommunications" title="Telecommunications">telecommunications</a>, for example in <a href="T-carrier" title="T-carrier">T-carrier</a>, is to insert, in a dedicated <a href="Time-division_multiplexing" title="Time-division multiplexing">time slot</a> within the frame, a noninformation <b>framing bit</b> that is used for synchronization of the incoming data with the receiver. In a <a href="Bit_stream" class="mw-redirect" title="Bit stream">bit stream</a>, framing bits are predictable (do not carry information), and occur at specified positions in the frame. Correct framing is verified when almost all framing bits (minus a small allowance for transmission errors) have their predicted values.</dd>
<dt>Syncword and flag sequence framing</dt>
<dd>Rather than a single bit, some systems use a multi-bit <a href="Syncword" title="Syncword">syncword</a> in each frame, or a <b>flag sequence</b> that marks the beginning and end of each frame. <a href="High-Level_Data_Link_Control" title="High-Level Data Link Control">High-Level Data Link Control</a> and similar systems use flag sequences.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup></dd>
<dt>CRC-based framing</dt>
<dd>Some telecommunications hardware uses <a href="CRC-based_framing" title="CRC-based framing">CRC-based framing</a>, where correct framing is verified when almost all frames have valid CRCs.</dd></dl>
<div class="mw-heading mw-heading2"><h2 id="Frame_synchronizer">Frame synchronizer</h2></div>
<p>In <a href="Telemetry" title="Telemetry">telemetry</a> applications, a <i>frame synchronizer</i> is used to locate frame boundaries within a serial <a href="Pulse-code_modulated" class="mw-redirect" title="Pulse-code modulated">pulse-code modulated</a> (PCM) binary stream.
</p><p>The frame synchronizer immediately follows the bit synchronizer in most telemetry applications. Without frame synchronization, <a href="Decommutation" class="mw-redirect" title="Decommutation">decommutation</a> is impossible.
</p>
<p>The frame synchronizer searches the incoming bit-stream for occurrences of the frame synchronization pattern. If the pattern persists for long enough that an accidental match is implausible, the synchronizer declares the data synchronized and available for decoding. If a large number of mis-matches occur, the synchronizer declares a loss of synchronization.
</p><p>The search can be sequential (only consider one starting point at a time), or multiple candidate starting points may be considered at once. Advanced techniques continue searching even while synchronization is established, so that, if synchronization is lost, by the time the loss is noticed a new frame start position has been found.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>
</p>
<p>It is not uncommon to have multiple levels of frame synchronization, where a series of frames is assembled into a larger "superframe" or "major frame". Individual frames are then "minor frames" within that superframe. Each frame contains a subframe ID (often a simple counter) which identifies its position within the superframe. A second frame synchronizer establishes superframe synchronization. This allows subcommutation, where some data is sent less frequently than every frame.
</p>
<div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2></div>
<ul><li><a href="Asynchronous_start-stop" class="mw-redirect" title="Asynchronous start-stop">Asynchronous start-stop</a></li>
<li><a href="Phase_synchronization" title="Phase synchronization">Phase synchronization</a></li>
<li><a href="Self-synchronizing_code" title="Self-synchronizing code">Self-synchronizing code</a></li>
<li><a href="Superframe" title="Superframe">Superframe</a></li></ul>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */
.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}
/* end https://en.wikipedia.org/ */
</style><div class="reflist">
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */
.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}
/* end https://en.wikipedia.org/ */
</style><cite id="CITEREFSimpson1994" class="citation cs1">Simpson, William A. (July 1994). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1662"><i>PPP in HDLC-like Framing</i></a>. Internet Engineering Task Force. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1662">10.17487/RFC1662</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1662">1662</a>.</cite></span>
</li>
<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1041539562">
/* start https://en.wikipedia.org/ */
.mw-parser-output .citation{word-wrap:break-word}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}
/* end https://en.wikipedia.org/ */
</style><span class="citation patent"><a rel="nofollow" class="external text" href="https://worldwide.espacenet.com/textdoc?DB=EPODOC&IDX=US5621773">US patent 5621773</a>, "Method and Apparatus for Fast Synchronization of T1 Extended Superframes", issued 1997-04-15, assigned to <a href="LSI_Logic_Corporation" class="mw-redirect" title="LSI Logic Corporation">LSI Logic Corporation</a></span><span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Apatent&rft.number=5621773&rft.cc=US&rft.title=Method+and+Apparatus+for+Fast+Synchronization+of+T1+Extended+Superframes&rft.assignee=%5B%5BLSI+Logic+Corporation%5D%5D&rft.date=1997-04-15"><span style="display: none;"> </span></span></span>
</li>
</ol></div></div>
<p><span class="citation FS1037C MS188"><span class="noviewer" typeof="mw:File"><span></span></span> This article incorporates <a href="Copyright_status_of_works_by_the_federal_government_of_the_United_States" title="Copyright status of works by the federal government of the United States">public domain material</a> from <cite class="citation cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20220122224547/https://www.its.bldrdoc.gov/fs-1037/fs-1037c.htm"><i>Federal Standard 1037C</i></a>. <a href="General_Services_Administration" title="General Services Administration">General Services Administration</a>. Archived from <a rel="nofollow" class="external text" href="https://www.its.bldrdoc.gov/fs-1037/fs-1037c.htm">the original</a> on 2022-01-22.</cite> (in support of <a href="MIL-STD-188" title="MIL-STD-188">MIL-STD-188</a>).</span>
</p>
<div class="mw-heading mw-heading3"><h3 id="Scientific_articles">Scientific articles</h3></div>
<ul><li><a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/abstract/document/1091127">J. L. Massey. "Optimum frame synchronization ". IEEE trans. comm., com-20(2):115-119, April 1972</a>.</li>
<li><a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/abstract/document/1094813">R Scholtz. "Frame synchronization techniques", <i>IEEE Transactions on Communications</i>, 1980</a>.</li>
<li>P. Robertson. "Optimal Frame Synchronization for Continuous and Packet Data Transmission", PhD Dissertation, 1995, Fortschrittberichte VDI Reihe 10, Nr. 376 <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110718231623/http://www.kn-s.dlr.de/People/Robertson/Papers/diss.pdf">PDF</a></li></ul></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2024-09-23" href="https://en.wikipedia.org/wiki/?title=Frame_synchronization&oldid=1247309993">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>
</body></html>